End-user computing Standard Requirements by Blokdyk Gerardus

Author:Blokdyk, Gerardus
Language: eng
Format: epub
Publisher: Emereo Publishing
Published: 2018-06-04T00:00:00+00:00

CRITERION #5: IMPROVE:

INTENT: Develop a practical solution. Innovate, establish and test the solution and to measure the results.

In my belief, the answer to this question is clearly defined:

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. For decision problems, how do you develop a decision statement?

<--- Score

2. Is a solution implementation plan established, including schedule/work breakdown structure, resources, risk management plan, cost/budget, and control plan?

<--- Score

3. Why improve in the first place?

<--- Score

4. What tools were used to evaluate the potential solutions?

<--- Score

5. Is Supporting End-user computing documentation required?

<--- Score

6. What does the ‘should be’ process map/design look like?

<--- Score

7. How does the team improve its work?

<--- Score

8. If you could go back in time five years, what decision would you make differently? What is your best guess as to what decision you’re making today you might regret five years from now?

<--- Score

9. Who will be responsible for documenting the End-user computing requirements in detail?

<--- Score

10. What is the risk?

<--- Score

11. How did the team generate the list of possible solutions?

<--- Score

12. How do we keep improving End-user computing?

<--- Score

13. How important is the completion of a recognized college or graduate-level degree program in the hiring decision?

<--- Score

14. What to do with the results or outcomes of measurements?

<--- Score

15. Do we cover the five essential competencies-Communication, Collaboration,Innovation, Adaptability, and Leadership that improve an organization’s ability to leverage the new End-user computing in a volatile global economy?

<--- Score

16. What communications are necessary to support the implementation of the solution?

<--- Score

17. Is the measure understandable to a variety of people?

<--- Score

18. How will we know that a change is improvement?

<--- Score

19. How do we improve productivity?

<--- Score

20. How do we measure improved End-user computing service perception, and satisfaction?

<--- Score

21. How do we measure risk?

<--- Score

22. Was a pilot designed for the proposed solution(s)?

<--- Score

23. How will you measure the results?

<--- Score

24. What actually has to improve and by how much?

<--- Score

25. Are improved process (‘should be’) maps modified based on pilot data and analysis?

<--- Score

26. Explorations of the frontiers of End-user computing will help you build influence, improve End-user computing, optimize decision making, and sustain change

<--- Score

27. What should a proof of concept or pilot accomplish?

<--- Score

28. Were any criteria developed to assist the team in testing and evaluating potential solutions?

<--- Score

29. What improvements have been achieved?

<--- Score

30. What actually has to improve and by how much?

<--- Score

31. What needs improvement?

<--- Score

32. How can we improve performance?

<--- Score

33. Who controls key decisions that will be made?

<--- Score

34. How do you manage and improve your End-user computing work systems to deliver customer value and achieve organizational success and sustainability?

<--- Score

35. What is the implementation plan?

<--- Score

36. Does the goal represent a desired result that can be measured?

<--- Score

37. What is the magnitude of the improvements?

<--- Score

38. Risk factors: what are the characteristics of End-user computing that make it risky?

<--- Score

39. Is there a cost/benefit analysis of optimal solution(s)?

<--- Score

40. How will the organization know that the solution worked?

<--- Score

41. Who will be responsible for

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.